<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Anatomy of a Bug</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="The Bugzilla Guide - 3.6.4 
    Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
REL="PREVIOUS"
TITLE="Create a Bugzilla Account"
HREF="myaccount.html"><LINK
REL="NEXT"
TITLE="Life Cycle of a Bug"
HREF="lifecycle.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide - 3.6.4 
    Release</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="myaccount.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Using Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="lifecycle.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="bug_page"
>5.3. Anatomy of a Bug</A
></H1
><P
>The core of Bugzilla is the screen which displays a particular
    bug. It's a good place to explain some Bugzilla concepts. 
    <A
HREF="http://landfill.bugzilla.org/bugzilla-3.6-branch/show_bug.cgi?id=1"
TARGET="_top"
>&#13;    Bug 1 on Landfill</A
>

    is a good example. Note that the labels for most fields are hyperlinks;
    clicking them will take you to context-sensitive help on that
    particular field. Fields marked * may not be present on every
    installation of Bugzilla.</P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;        <EM
>Product and Component</EM
>: 
        Bugs are divided up by Product and Component, with a Product
        having one or more Components in it. For example,
        bugzilla.mozilla.org's "Bugzilla" Product is composed of several
        Components: 
        <P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13;        <EM
>Administration:</EM
>
        Administration of a Bugzilla installation.</TD
></TR
><TR
><TD
>&#13;        <EM
>Bugzilla-General:</EM
>
        Anything that doesn't fit in the other components, or spans
        multiple components.</TD
></TR
><TR
><TD
>&#13;        <EM
>Creating/Changing Bugs:</EM
>
        Creating, changing, and viewing bugs.</TD
></TR
><TR
><TD
>&#13;        <EM
>Documentation:</EM
>
        The Bugzilla documentation, including The Bugzilla Guide.</TD
></TR
><TR
><TD
>&#13;        <EM
>Email:</EM
>
        Anything to do with email sent by Bugzilla.</TD
></TR
><TR
><TD
>&#13;        <EM
>Installation:</EM
>
        The installation process of Bugzilla.</TD
></TR
><TR
><TD
>&#13;        <EM
>Query/Buglist:</EM
>
        Anything to do with searching for bugs and viewing the
        buglists.</TD
></TR
><TR
><TD
>&#13;        <EM
>Reporting/Charting:</EM
>
        Getting reports from Bugzilla.</TD
></TR
><TR
><TD
>&#13;        <EM
>User Accounts:</EM
>
        Anything about managing a user account from the user's perspective.
        Saved queries, creating accounts, changing passwords, logging in,
        etc.</TD
></TR
><TR
><TD
>&#13;        <EM
>User Interface:</EM
>
        General issues having to do with the user interface cosmetics (not
        functionality) including cosmetic issues, HTML templates,
        etc.</TD
></TR
></TBODY
></TABLE
><P
></P
>
        </P
></LI
><LI
><P
>&#13;        <EM
>Status and Resolution:</EM
>

        These define exactly what state the bug is in - from not even
        being confirmed as a bug, through to being fixed and the fix
        confirmed by Quality Assurance. The different possible values for
        Status and Resolution on your installation should be documented in the
        context-sensitive help for those items.</P
></LI
><LI
><P
>&#13;        <EM
>Assigned To:</EM
>
        The person responsible for fixing the bug.</P
></LI
><LI
><P
>&#13;        <EM
>*QA Contact:</EM
>
        The person responsible for quality assurance on this bug.</P
></LI
><LI
><P
>&#13;        <EM
>*URL:</EM
>
        A URL associated with the bug, if any.</P
></LI
><LI
><P
>&#13;        <EM
>Summary:</EM
>
        A one-sentence summary of the problem.</P
></LI
><LI
><P
>&#13;        <EM
>*Status Whiteboard:</EM
>
        (a.k.a. Whiteboard) A free-form text area for adding short notes
        and tags to a bug.</P
></LI
><LI
><P
>&#13;        <EM
>*Keywords:</EM
>
        The administrator can define keywords which you can use to tag and
        categorise bugs - e.g. The Mozilla Project has keywords like crash
        and regression.</P
></LI
><LI
><P
>&#13;        <EM
>Platform and OS:</EM
>
        These indicate the computing environment where the bug was
        found.</P
></LI
><LI
><P
>&#13;        <EM
>Version:</EM
>
        The "Version" field is usually used for versions of a product which
        have been released, and is set to indicate which versions of a
        Component have the particular problem the bug report is
        about.</P
></LI
><LI
><P
>&#13;        <EM
>Priority:</EM
>
        The bug assignee uses this field to prioritize his or her bugs.
        It's a good idea not to change this on other people's bugs.</P
></LI
><LI
><P
>&#13;        <EM
>Severity:</EM
>
        This indicates how severe the problem is - from blocker
        ("application unusable") to trivial ("minor cosmetic issue"). You
        can also use this field to indicate whether a bug is an enhancement
        request.</P
></LI
><LI
><P
>&#13;        <EM
>*Target:</EM
>
        (a.k.a. Target Milestone) A future version by which the bug is to
        be fixed. e.g. The Bugzilla Project's milestones for future
        Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not
        restricted to numbers, thought - you can use any text strings, such
        as dates.</P
></LI
><LI
><P
>&#13;        <EM
>Reporter:</EM
>
        The person who filed the bug.</P
></LI
><LI
><P
>&#13;        <EM
>CC list:</EM
>
        A list of people who get mail when the bug changes.</P
></LI
><LI
><P
>&#13;        <EM
>*Time Tracking:</EM
>
        This form can be used for time tracking.
        To use this feature, you have to be blessed group membership
        specified by the <SPAN
CLASS="QUOTE"
>"timetrackinggroup"</SPAN
> parameter.
        <P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13;        <EM
>Orig. Est.:</EM
>
        This field shows the original estimated time.</TD
></TR
><TR
><TD
>&#13;        <EM
>Current Est.:</EM
>
        This field shows the current estimated time.
        This number is calculated from <SPAN
CLASS="QUOTE"
>"Hours Worked"</SPAN
>
        and <SPAN
CLASS="QUOTE"
>"Hours Left"</SPAN
>.</TD
></TR
><TR
><TD
>&#13;        <EM
>Hours Worked:</EM
>
        This field shows the number of hours worked.</TD
></TR
><TR
><TD
>&#13;        <EM
>Hours Left:</EM
>
        This field shows the <SPAN
CLASS="QUOTE"
>"Current Est."</SPAN
> -
        <SPAN
CLASS="QUOTE"
>"Hours Worked"</SPAN
>.
        This value + <SPAN
CLASS="QUOTE"
>"Hours Worked"</SPAN
> will become the
        new Current Est.</TD
></TR
><TR
><TD
>&#13;        <EM
>%Complete:</EM
>
        This field shows what percentage of the task is complete.</TD
></TR
><TR
><TD
>&#13;        <EM
>Gain:</EM
>
        This field shows the number of hours that the bug is ahead of the
        <SPAN
CLASS="QUOTE"
>"Orig. Est."</SPAN
>.</TD
></TR
><TR
><TD
>&#13;        <EM
>Deadline:</EM
>
        This field shows the deadline for this bug.</TD
></TR
></TBODY
></TABLE
><P
></P
>
        </P
></LI
><LI
><P
>&#13;        <EM
>Attachments:</EM
>
          You can attach files (e.g. testcases or patches) to bugs. If there
          are any attachments, they are listed in this section.  Attachments are
          normally stored in the Bugzilla database, unless they are marked as
          Big Files, which are stored directly on disk.
        </P
></LI
><LI
><P
>&#13;        <EM
>*Dependencies:</EM
>
        If this bug cannot be fixed unless other bugs are fixed (depends
        on), or this bug stops other bugs being fixed (blocks), their
        numbers are recorded here.</P
></LI
><LI
><P
>&#13;        <EM
>*Votes:</EM
>
        Whether this bug has any votes.</P
></LI
><LI
><P
>&#13;        <EM
>Additional Comments:</EM
>
        You can add your two cents to the bug discussion here, if you have
        something worthwhile to say.</P
></LI
></OL
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="myaccount.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="lifecycle.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Create a Bugzilla Account</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="using.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Life Cycle of a Bug</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>